language en
License:
http://insertlicenseURIhere.example.org
Visualization:
Visualize with WebVowl
Provenance of this page
Ontology Specification Draft

[Ontology Name]: Overview back to ToC

This ontology has the following classes and properties.

Classes

Cross-reference for [Ontology Name] classes, object properties and data properties back to ToC

This section provides details for each class and property defined by [Ontology Name].

Classes

Availability Tacticc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#AvailabilityTactic

A tactic designed to enable a system to endure faults so that the service being delivered remains compliant with its specification. The goal is to keep faults from becoming failures or to bound the effects of faults and make repair possible.
has super-classes
tactic c
has sub-classes
Detect Faults c, Prevent Faults c, Recover from Faults c

Control Resource Demandc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#ControlResourceDemand

A performance tactic that operates on the demand side to produce smaller demand on the resources that will have to service the events.
Example
Techniques: Manage Sampling Rate, Limit Event Response, Prioritize Events, Reduce Overhead, Bound Execution Times, Increase Resource Efficiency.
has super-classes
Performance Tactic c

Defer Bindingc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#DeferBinding

A modifiability tactic that defers binding decisions to later in the lifecycle (compile time, deployment time, or runtime) to reduce the cost of making changes. Techniques include component replacement, compile-time parameterization, configuration-time binding, runtime registration, dynamic lookup, plug-ins, publish-subscribe, shared repositories, and polymorphism.
Example
Techniques: Component Replacement, Compile-Time Parameterization, Configuration-Time Binding, Runtime Registration, Dynamic Lookup, Interpret Parameters, Startup-Time Binding, Name Servers, Plug-ins, Publish-Subscribe, Shared Repositories, Polymorphism.
has super-classes
Modifiability Tactic c

Detect Attacksc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#DetectAttacks

A category of security tactics focused on detecting attacks, using techniques such as intrusion detection systems, monitoring, and audit trails.
Example
Techniques: Detect Intrusion, Detect Service Denial, Verify Message Integrity, Detect Message Delay.
has super-classes
Security Tactic c

Detect Faultsc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#DetectFaults

A category of availability tactics focused on detecting faults before they cause failures, using techniques such as ping/echo, heartbeat, and exception monitoring.
Example
Techniques: Ping/Echo, Heartbeat, Timestamp, Sanity Checking, Condition Monitoring, Voting, Exception Detection, Self-Test.
has super-classes
Availability Tactic c

Increase Cohesionc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#IncreaseCohesion

A modifiability tactic that increases the semantic coherence within a module so that changes are localized to fewer modules.
has super-classes
Modifiability Tactic c

Interoperability Tacticc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#InteroperabilityTactic

A tactic designed to enable meaningful exchange of information and services between systems that were not necessarily designed to work together.
has super-classes
tactic c
has sub-classes
Locate c, Manage Interfaces c

Locatec back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#Locate

An interoperability tactic focused on discovering the location and identity of services or systems to communicate with, using techniques such as service discovery and directory lookup.
Example
Techniques: Discover Service, Use Known Interface.
has super-classes
Interoperability Tactic c

Manage Interfacesc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#ManageInterfaces

An interoperability tactic focused on managing the interfaces between systems, using techniques such as orchestration, adapters, and interface standardization.
Example
Techniques: Orchestrate, Tailor Interface.
has super-classes
Interoperability Tactic c

Manage Resourcesc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#ManageResources

A performance tactic that operates on the response side to make the resources at hand work more effectively in handling the demands put to them.
Example
Techniques: Increase Resources, Introduce Concurrency, Maintain Multiple Copies of Computations, Maintain Multiple Copies of Data, Bound Queue Sizes, Schedule Resources.
has super-classes
Performance Tactic c

Modifiability Tacticc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#ModifiabilityTactic

A tactic designed to reduce the cost and risk of making changes to a system by controlling the complexity of modifications.
has super-classes
tactic c
has sub-classes
Defer Binding c, Increase Cohesion c, Reduce Coupling c, Reduce Size of a Module c

Performance Tacticc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#PerformanceTactic

A tactic designed to generate a response to an event within a specified time constraint by controlling resource demand or managing resources.
has super-classes
tactic c
has sub-classes
Control Resource Demand c, Manage Resources c

Preparation and Repairc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#PreparationAndRepair

Recovery tactics based on combinations of retrying a computation or introducing redundancy to prepare for and repair faults.
Example
Techniques: Active Redundancy (Hot Spare), Passive Redundancy (Warm Spare), Spare, Exception Handling, Rollback, Software Upgrade, Retry, Ignore Faulty Behavior, Degradation, Reconfiguration.
has super-classes
Recover from Faults c

Prevent Faultsc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#PreventFaults

A category of availability tactics focused on preventing faults from occurring in the first place, using techniques such as removal from service, transactions, and process monitors.
Example
Techniques: Removal from Service, Transactions, Predictive Model, Exception Prevention, Increase Competence Set.
has super-classes
Availability Tactic c

React to Attacksc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#ReactToAttacks

A category of security tactics focused on reacting to detected attacks, using techniques such as revoking access, locking accounts, and alerting administrators.
Example
Techniques: Revoke Access, Lock Computer, Inform Actors.
has super-classes
Security Tactic c

Recover from Attacksc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#RecoverFromAttacks

A category of security tactics focused on recovering from successful attacks, using techniques such as restoring state, maintaining audit trails, and applying availability tactics.
Example
Techniques: Maintain Audit Trail, Restore (using availability tactics).
has super-classes
Security Tactic c

Recover from Faultsc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#RecoverFromFaults

A category of availability tactics focused on recovering the system to a correct state after a fault has been detected.
has super-classes
Availability Tactic c
has sub-classes
Preparation and Repair c, Reintroduction c

Reduce Couplingc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#ReduceCoupling

A modifiability tactic that reduces dependencies between modules so that a change in one module has less impact on others.
Example
Techniques: Encapsulate, Use an Intermediary, Restrict Dependencies, Refactor, Abstract Common Services.
has super-classes
Modifiability Tactic c

Reduce Size of a Modulec back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#ReduceSizeOfAModule

A modifiability tactic that splits large modules into smaller, more manageable units to reduce the scope of changes.
Example
Techniques: Split Module, Increase Semantic Coherence.
has super-classes
Modifiability Tactic c

Reintroductionc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#Reintroduction

A recovery tactic where a failed component is reintroduced into service after it has been corrected.
Example
Techniques: Shadow, State Resynchronization, Escalating Restart, Non-Stop Forwarding.
has super-classes
Recover from Faults c

Resist Attacksc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#ResistAttacks

A category of security tactics focused on resisting and preventing attacks from succeeding, using techniques such as authentication, authorization, encryption, and input validation.
Example
Techniques: Identify Actors, Authenticate Actors, Authorize Actors, Limit Access, Limit Exposure, Encrypt Data, Separate Entities, Change Default Settings.
has super-classes
Security Tactic c

Security Tacticc back to ToC or Class ToC

IRI: https://meta.linked.archi/tactics#SecurityTactic

A tactic designed to protect data and information from unauthorized access while still providing access to authorized people and systems. Security tactics address attacks — unauthorized attempts to access data or services, modify data, or deny services to legitimate users.
has super-classes
tactic c
has sub-classes
Detect Attacks c, React to Attacks c, Recover from Attacks c, Resist Attacks c

Legend back to ToC

c: Classes

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.